All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

I have read the CLA Document and I hereby sign the CLA

recheck

@julian-smith-artifex-com any thoughts on this?

I do not think that this PR is able to solve what seems to be your intention.

1. The list page.get_fonts() reports the font entries in a page's object definition in /Resources. No more - no less. The fonts actually used may be a true subset of those.
2. The font names appearing in page.get_text("dict") need not (exactly) equal the font names mentioned in that list, and this can never be guaranteed whatever we do. Reasons include:
   • By default, we omit the subset prefix "ABCDEF+" from the font name. You can request to include them by setting a global option pymupdf.TOOLS.set_subset_fontnames(True).
   • The name in "dict" is reported by MuPDF which looks at the self identification in the font file - not at the PDF object definition. Both names may be (and frequently are) different. Also, MuPDF only returns up to 31 bytes of the font name - the PDF definition may be much longer. So the "dict" output will never be longer than 31 bytes.
   • Text extraction works for all document types - not just PDF. So we cannot expect perfect parallelism with get_fonts(), which is a PDF-only function.
   • As a consequence of the above, you may see identical font names in "dict" outputs although the respective text pieces in fact are displayed by truly different fonts in the PDF - even when subset fontnames is True.

thank you for the clarification. the global option will help me.

I didn't realize how much integration with mupdf there was with the font system. thanks again.

Thank you for your understanding and you willingness to contribute!